Skip to content

Conversation

@lmolkova
Copy link
Member

@lmolkova lmolkova commented Jan 3, 2026

Fixes #1853

Comment on lines 212 to 213
Don't try to capture all available properties as span attributes. Telemetry is
lossy, and it's important to assess the value-to-cost ratio of each referenced attribute.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't follow the tie in to being lossy

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved this to attributes section and replaced with

Only include attributes that bring clear value - this allows keeping telemetry
volume and performance overhead low. Don't try to capture all available details.
When in doubt, don't reference additional attributes - they can be added incrementally
based on feedback.

- When the span starts and ends.
- If this span represents a client call, specify whether it captures the logical call
(as observed by the API caller) or the physical call (per-try/per-attempt).
- Define a span per different operation type.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what this is saying, maybe a short example could help?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated to

  • Define a different span for different operations - e.g., when spans have different
    kinds or a significantly different set of attributes.
    For example, HTTP client and server spans are two independent definitions.
    Messaging publishing and receiving are also different span types.

@lmolkova lmolkova force-pushed the how-to-define-spans branch from 0b17b67 to a2914f1 Compare January 9, 2026 21:34
@lmolkova lmolkova added the Skip Changelog Label to skip the changelog check label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Changelog Label to skip the changelog check

Projects

Development

Successfully merging this pull request may close these issues.

SemConv guidance: document how to define spans

3 participants